Add environment variables using action inputs
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
Research direction
Start by reviewing the reusable GitHub Action workflow and the proposed environment-variable step in the issue, then inspect linked pull request #21. Confirm how action inputs, variables, and secrets are currently exposed before implementing the deployment update. Done means configured environment variables are applied during deployment without breaking the existing action flow.
Written by the indexing model from the issue text.
Description
In some cases, an environment variable is necessary for the app to deploy/run correctly (e.g DB credentials).
I suggest adding a separate step right after creating the app that might look like this.
The condition for when to run this step can also depend on whether any ENV_VARIABLEs have been configured
- name: Set up DE application environment
shell: bash
if: github.event.action != 'closed'
run: |
IFS = $VAR_SEPERATOR
for env in $(read -ra env <<< $ENV_VARIABLES) ; do
de --no-keyfile apps update --name ${{ env.APP_NAME }} --add-environment-variable $env
done
env:
DASH_ENTERPRISE_HOST: ${{ vars.DASH_ENTERPRISE_URL }}
DASH_ENTERPRISE_USERNAME: ${{ vars.DASH_ENTERPRISE_USERNAME }}
DASH_ENTERPRISE_PASSWORD: ${{ secrets.DASH_ENTERPRISE_PASSWORD }}
APP_NAME: ${{ vars.APP_NAME }}
ENV_VARIABLES: ${{ secrets.ENV_VARIABLES }}
VAR_SEPERATOR: ${{ vars.VAR_SEPERATOR }}
- Dominant language
- No language data
- Stars
- 4
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from plotly/de-deploy
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Add support for DE4 Open
All issues in plotly/de-deploy
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
vicharanashala/fln#564 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
haskell-actions/setup#152 ·
-
feature-request helm
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gravitational/teleport#69785 ·
-
A cancelled tests run makes the coverage comment workflow fail and reports it as a red check on main Openarea: ci bug perceived difficulty: 3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Nitjsefnie-Harness-Commons/daedalus#921 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
TencentCloud/Octop#1007 ·