YAML file requires different amounts of indentation for different nodes - yaml

I'm attempting to write a YAML config script for a load testing utility called Artillery.
The YAML syntax is not making any sense to me though. Artillery appears to deserialize the YAML to a Javascript object syntax so it expects nodes in the YAML file to have a certain structure.
config:
target: https://mhhs-prod-webapp.azurewebsites.net/
phases:
- duration: 60
arrivalRate: 50
scenarios:
- flow:
- get:
url: '/'
Given the above file though it fails complaining that 'get' must be of type object. In the file above the get node has a child node url of key value type, so I'm expecting it to be of type object.
After much trial and error I've managed to get it to work using the following layout.
config:
target: https://mhhs-prod-webapp.azurewebsites.net/
phases:
- duration: 60
arrivalRate: 50
scenarios:
- flow:
- get:
url: '/'
But the bizarre thing is that this file is identical to the previous one apart from the fact that the url node is indented 4 spaces instead of the 2 spaces of indentation used throughout the rest of the file.
Is this correct? I'm having trouble finding an explanation of YAML that is understandable but so far I haven't come across anything that suggests that different amounts of indentation do completely different things.

Hohoho, I understand how you feel about YAML indentations.
It's like Python-based indentation but with a mix of JSON.
In your code:
config:
...
scenarios:
- flow:
- get:
url: '/'
"url" looks like a child of "flow" since it has an indent like so.
It can go in a couple of routes.
Route #1: (Where "url" is under "flow:")
...
scenarios:
- flow:
- get:
- url: '/'
Route #2: (Where "url" is under "get:")
...
scenarios:
- flow:
- get:
- url: '/'
Route #3: (Where "url" is under~ uhm...)
config:
...
scenarios:
...
url: '/'

Related

How to add item to YML collection conditionally using Serverless framework?

Given I have the following defined in a YML file for a resource:
Type: AWS::Cognito::UserPoolClient
CallbackURLs:
- "my-first-url"
How can I add a second item when only certain conditions are met? Unfortuantely it is not possible to simply set it to an empty string or null as it fails deployment validation. E.G something like:
Type: AWS::Cognito::UserPoolClient
CallbackURLs:
- "my-first-url"
- myCondition ? "" : undefined // Omit item
Is this possible in any way at all? Happy to use Plugin solutions etc.
You can use a CloudFormation condition like Fn::If to conditionally create stack resources. The CloudFormation documentation about conditions has all the details but somehting like this should get you started:
resources:
Conditions:
my_condition: !Equals [value_1, value_2]
Resources:
MyUserPool:
Type: AWS::Cognito::UserPoolClient
CallbackURLs:
- "my-first-url"
- !If [my_condition, "...", !Ref "AWS::NoValue"]
Replace the content of my_condition with your condition. It is referenced later in the Fn::If (the example uses the shorthand for Fn::If).
The AWS::NoValue is a pseudo parameter which can be used as a return value to remove the corresponding property. It should work here to remove the list item but I'm not sure about it, you'll need to test.

yaml workflow missing start tag

I'm trying to use Go client to programmatically manage workflows. I'm using yaml, this is my workflow:
name: order-process
tasks:
- id: collect-money
type: payment-service
- id: fetch-items
type: inventory-service
switch:
- case: totalPrice > 100
goto: ship-parcel-with-insurance
- default: ship-parcel
- id: ship-parcel-with-insurance
type: shipment-service-premium
end: true
- id: ship-parcel
type: shipment-service
And when I deploy this, I can't visualize it in camunda operate, the page is stuck on loading
and I have this error in console:
Error: unparsable content detected
line: 0
column: 0
nested error: missing start tag
we are sorry but Operate only supports BPMN XML deployments at the moment. The YAML support in Zeebe is only rudimentary and not intended for real-world use cases. It becomes really hard to model complex processes with yaml, which is easily possible with BPMN. We highly encourage you to switch to the Zeebe Modeler to create your workflow models.
If you want to discuss this further, we are happy to welcome you in one of our community channels.

Serverless Framework function HTTP trigger event configuration

Say I have a serverless app that uses multiple Lambda functions triggered by HTTP event, where they all follow a similar URL format (same path parameter) - for example:
Function 1 path is: events/{id}
Function 2 path is: events/{id}/attendees
Function 3 path is: events/{id}/join
My serverless.yml is starting to look like:
...
functions:
get_event:
handler: handler.getEvent
events:
- http:
path: events/{id}
method: get
cors: true
request:
parameters:
paths:
id: true
get_event_attendees:
handler: handler.getEventAttendees
events:
- http:
path: events/{id}/attendees
method: get
cors: true
request:
parameters:
paths:
id: true
join_event:
handler: handler.joinEvent
events:
- http:
path: events/{id}/join
method: post
cors: true
request:
parameters:
paths:
id: true
What is a good way to refactor these http event declarations to reduce the redundancy?
I'm aware of the serverless variables syntax, but unsure of how I can make something more like a function, that accepts as arguments the different path parameters, and returns the appropriate YML.
I believe doing something like:
custom:
httpRequest:
parameters:
paths:
id: true
...
functions:
get_event:
handler: handler.getEvent
events:
- http:
path: events/{id}
method: get
request: ${self:custom:httpRequest}
get_event_attendees:
handler: handler.getEventAttendees
events:
- http:
path: events/{id}/attendees
method: get
request: ${self:custom:httpRequest}
...
only works if all the HTTP functions I ever write only have that one path parameter id.
Personally I wouldn't worry about it. There is some level of verbosity needed because of the sheer number of elements that can be configured but the redundancy in no way negatively affects the performance of your application. And while it may seem redundant, what you really have is the granularity to affect change very uniquely across your functions as well as the clarity to see what the differences are between them.
If you want to clean up the serverless.yml overall look at breaking out into separate files perhaps for all the function definitions or perhaps per event https://serverless.com/framework/docs/providers/aws/guide/variables/#reference-variables-in-other-files
That will probably server you better by keeping related entities together but segregated so there's less cognitive load when looking at the base serverless.yml file.

How to change one value in an associative array referenced by Node

So I apologize in advance if I use yaml terminology wrong I am pretty new to it.
So I have this item in a list that is an associative array and I would like to use a node to repeat it multiple times in the file but I need to change one value in a sub array in it and I don't know how to do it without overwriting the entire array.
So here is the item in the list
- &def_service
type: service
name: Remote Service
config:
machine: ''
version: '1.0.0'
apikey: VALUE_I_WANT_TO_CHANGE
and I what I've tried to do is
- <<: *def_service
config:
apikey: NEW_VALUE
but that just overwrites the entire array so config is just
{config:{apikey:NEW_VALUE}}
I would be very grateful for an answer here I am pretty stuck.
Ok so an answer that occurred to me maybe not the best answer is just to introduce another variable for the config array like this.
- &def_service
type: service
name: Remote Service
config: &service_config
machine: ''
version: '1.0.0'
apikey: VALUE_I_WANT_TO_CHANGE
so to reference it I did this
- <<: *def_service
config:
<<: *service_config
apikey: NEW_VALUE
YAML is not a programming language. It is designed for data representation, not for data transformation.
The merge key you use (<<) is not part of the YAML specification. It is part of the YAML type repository, which is outdated (since it is defined for YAML 1.1). Therefore, your question is highly dependendent on the YAML processor you use. One processor might implement it while another does not.
Since you have a specific problem, it would probably be better to write YAML tailored to your problem, and then handle it in your code (assuming that you are in charge of the code). Something like this:
- !config_base
&def_service
type: service
name: Remote Service
config: &service_config
machine: ''
version: '1.0.0'
apikey: VALUE_I_WANT_TO_CHANGE
- !config_child
base: *def_service
substitutions:
config:
apikey: NEW_VALUE
You can then write code that does the substitution inside your deserialized YAML structure.

Kwalify YAML Validation - Use regexes in key names?

I'm using Kwalify for schema validation. One part of the YAML document actually does want to allow for key names of a certain type in a mapping.
I see that Kwalify support regexes for the values in a mapping, but I see no such mention of support for using regexes in the keys in a mapping. Here's what I'd like to support validating:
test-element:
sub-element-1: test
sub-element-2:
element-with-pattern-1: test1
element-with-pattern-2: test2
So I don't know what some key names will exactly be in advance (shown here with the fake names "element-with-pattern-*", but I do know that they should correspond to a pattern defined by a regex.
Is this possible to validate using Kwalify?
To check this:
parent_key:
random_key1: url1
random_key2: url2
you should use "Default of Mapping", here is schema example:
type: map
mapping:
"parent_key":
type: map
mapping:
"=":
type: str
http://www.kuwata-lab.com/kwalify/ruby/users-guide.02.html#tips-default
I do not believe it's possible given the current state of the code.
I'm actually in a similar situation, which I found out (the hard way) does not work well for validation in the Kwalify context. I've begun migrating away from flexible key names into a paradigm where I can specifically define the schema.
For example, I migrated this:
parent_key:
random_key1: url1
random_key2: url2
To:
parent_key:
- name: random_key1
url: url1
- name: random_key2
url: url2
With the latter syntax, you can validate like this:
"parent_key":
type: seq
sequence:
- type: map
mapping:
"name":
type: str
required: yes
"url":
type: str
required: yes
Within that context, you can add a pattern regex validators to either name or url that should allow you to achieve your goal.

Resources