Repository navigation
Conversation
GitLab syncs can now target a GitLab environment scope. Describe the new GitLab Environment Scope picker in the sync setup steps, and add an Environment scopes section covering: - how each sync manages only the variables in its own scope, with an example mapping of Phase Environments to GitLab environments - using scoped secrets in .gitlab-ci.yml jobs with `environment:` - syncs created before scopes were available - the one sync per project or group and scope rule - the GitLab Premium or Ultimate requirement for scoped group variables Recapture the Configure sync screenshot with the scope picker and add a screenshot of the scope dropdown, using the standard mock org and cursor. The Markdown copy in public/ is regenerated from the MDX.
3 of 6 tasks
Deploying phase-docs with
|
| Latest commit: |
2dd3481
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d5fd12e1.phase-docs.pages.dev |
| Branch Preview URL: | https://feat--gitlab-environment-sco.phase-docs.pages.dev |
Explain where the scope dropdown's suggestions come from for groups, and that variables moved to other scopes by hand need their own sync (or deleting) when an older sync is recreated with a scope.
Older syncs can't tell which variable to change when a secret exists in several environment scopes. Say what they do then and how to fix it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Documents GitLab CI environment scopes for GitLab syncs, added in phasehq/console#1044 (closes phasehq/console#1043).
Changes
review/*, Staging →staging, Production →production), and how to combine a*sync with scoped syncs..gitlab-ci.ymlexample usingenvironment:so jobs receive scoped variables.*and updating variables moved to other scopes.public/assets/images/platform-integrations/gitlab/:gitlab-setup-sync.webp: recaptured with the scope picker.gitlab-sync-card.webp: recaptured with a scoped sync.gitlab-setup-sync-environment-scope.webp: new, showing the dropdown.public/integrations/platforms/gitlab-ci.mdregenerated withscripts/export-mdx-to-md.js.The screenshots follow the existing Console screenshot conventions:
phase/backend).They're captured from a local Console running the console PR against a self-hosted GitLab. The behaviour described was checked against that GitLab instance: scope precedence through pipeline runs, and older syncs (created with the code on
main) through the variables API, before and after switching to the console PR.