Frontend changes for additional providers

**Environment page:**
- [x] Add provider button below Cloud Provider section
- [x] Render provider tab contents as additional entries under Cloud Provider section
- [x] Cloud Provider entries that are not created via cluster hack (and don't overlap with environment variables) should have an edit option that scrolls the provider card/tab into view
- [x] When possible, all providers should be editable in the provider tab

**Deployment editor:**
- [x] Iterate through connections to determine which ResourceTypes can be used instead of limiting to the primary provider

**Tangentially related (environment page):**
- [x] Cloud Provider entry should have key value pairs regardless of whether a gitlab cluster was created with the environment
- [ ] As above, but ensure this doesn't break things when the current user doesn't have access to environment variables

**Updates:**
- [x] Edit providers in a modal
- [x] Prevent multiple providers of the same type

**Environment page:**
- [x] Add provider button below Cloud Provider section
- [x] Render provider tab contents as additional entries under Cloud Provider section
- [x] Cloud Provider entries that are not created via cluster hack (and don't overlap with environment variables) should have an edit option that scrolls the provider card/tab into view
- [x] When possible, all providers should be editable in the provider tab

**Deployment editor:**
- [x] Iterate through connections to determine which ResourceTypes can be used instead of limiting to the primary provider

**Tangentially related (environment page):**
- [x] Cloud Provider entry should have key value pairs regardless of whether a gitlab cluster was created with the environment
- [ ] As above, but ensure this doesn't break things when the current user doesn't have access to environment variables

**Updates:**
- [x] Edit providers in a modal
- [ ] Prevent multiple providers of the same type

**Environment page:**
- [x] Add provider button below Cloud Provider section
- [x] Render provider tab contents as additional entries under Cloud Provider section
- [x] Cloud Provider entries that are not created via cluster hack (and don't overlap with environment variables) should have an edit option that scrolls the provider card/tab into view
- [x] When possible, all providers should be editable in the provider tab

**Deployment editor:**
- [ ] Iterate through connections to determine which ResourceTypes can be used instead of limiting to the primary provider

**Tangentially related (environment page):**
- [x] Cloud Provider entry should have key value pairs regardless of whether a gitlab cluster was created with the environment
- [ ] As above, but ensure this doesn't break things when the current user doesn't have access to environment variables

There was no card header for the outer card on aws/gcp before this
change

**Environment page:**
- [x] Add provider button below Cloud Provider section
- [x] Render provider tab contents as additional entries under Cloud Provider section
- [ ] Cloud Provider entries that are not created via cluster hack (and don't overlap with environment variables) should have an edit option that scrolls the provider card/tab into view
- [ ] When possible, all providers should be editable in the provider tab

**Deployment editor:**
- [ ] Iterate through connections to determine which ResourceTypes can be used instead of limiting to the primary provider

**Tangentially related (environment page):**
- [x] Cloud Provider entry should have key value pairs regardless of whether a gitlab cluster was created with the environment
- [ ] As above, but ensure this doesn't break things when the current user doesn't have access to environment variables

Update instructions for external users in the GitHub mirrored repo component

Implement deployment editor local deploy button

Connected repos: use mixin, always hit setup credentials, hardcode username

Update image source repository username, fix inconsistent BLUEPRINT_PROJECT_URL matching for deploy token registration

Update image source repository username, fix inconsistent BLUEPRINT_PROJECT_URL matching for deploy token registration

Co-authored-by: Adam Souzis <adam@onecommons.org>

Implement atomic deployment changes

Also additions/fixes with:
* trigger service account deployment for GCP
* fix deployment blueprint source with clones
* add fields to primary provider properties list,
* post environment variables before commiting changes to dashboard
  repository

Improve membership access test script & and assertion

Change deploy feedback message and add tooltip to primary card validation

Andrew Breidenbach authored 2 years ago and Adam Souzis committed 2 years ago

Disregard ensemble.json ResourceType dictionary when editing deployments https://github.com/onecommons/gitlab-oc/issues/1275

Andrew Breidenbach authored 2 years ago and Adam Souzis committed 2 years ago

https://github.com/onecommons/gitlab-oc/issues/1280