-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FIX: More bugs in Manual Deploy Workflow #190
Conversation
* Inputs need to be passed in from the workflow dispatch to the base workflow as booleans, so use a fromJson function to flip them. * Rename the env-name input to environment so that it matches with the workflow dispatch name. * Pass the environment string, not the name of the variable. * Add prod to list of environments we can change the task count for.
@@ -9,6 +9,7 @@ on: | |||
options: | |||
- dev | |||
- staging | |||
- prod |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can change the task count for prod now.
env-name: | ||
environment: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rename this input, with cascading changes in the deploy workflows that call deploy-base.yaml
deploy-tableau-publisher: github.envent.inputs.deploy-tableau-publisher | ||
# pass the inputs from the workflow dispatch through to the deploy base. the booleans are | ||
# converted to strings, so flip them back using fromJson function | ||
environment: ${{ github.event.inputs.environment }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i was passing the string of the variable name before 😵💫
deploy-ingestion: ${{ fromJson(github.event.inputs.deploy-ingestion) }} | ||
deploy-rail-pm: ${{ fromJson(github.event.inputs.deploy-rail-pm) }} | ||
deploy-tableau-publisher: ${{ fromJson(github.event.inputs.deploy-tableau-publisher) }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
using fromJson
converts these from strings back to bools.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would you want the fromJson
on the inside or the outside of ${{..}}
here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
expressions go inside.
i still find all of the syntax rules a bit hard to follow, but i'm sure they stem from some weird backend interpreter they have to use.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One question, but otherwise LGTM
Inputs need to be passed in from the workflow dispatch to the base workflow as booleans, so use a fromJson function to flip them.
Rename the env-name input to environment so that it matches with the workflow dispatch name.
Pass the environment string, not the name of the variable.
Add prod to list of environments we can change the task count for.