You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The example should highlight using ESC to grab OIDC creds instead of scripting aws in bash, at least as a first option. We can keep the bash scripting to get AWS creds, but I might make it an appendix or something less prominent.
@dschaller Can you confirm that a bash script is still the best we can do as far as orchestration of the actual CI/CD steps, and that we have yet to develop the GL equivalent of a GH action? (No shade - I know that the ecosystem may not be as easy for us to develop a solution for.)
This should be addressed alongside #12515 if there's anything additional actionable in the aforementioned issue - I would just make sure it's clear which steps are in the GL UI.
The text was updated successfully, but these errors were encountered:
https://www.pulumi.com/docs/iac/using-pulumi/continuous-delivery/gitlab-ci/
This page is out of date. Here's what should change:
aws
in bash, at least as a first option. We can keep the bash scripting to get AWS creds, but I might make it an appendix or something less prominent.This should be addressed alongside #12515 if there's anything additional actionable in the aforementioned issue - I would just make sure it's clear which steps are in the GL UI.
The text was updated successfully, but these errors were encountered: