Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Publish Starter deployment failure due to incorrect environment credentials #30482

Closed
4 tasks
dcolina opened this issue Oct 29, 2024 · 1 comment · Fixed by #30483 or #30509
Closed
4 tasks

Publish Starter deployment failure due to incorrect environment credentials #30482

dcolina opened this issue Oct 29, 2024 · 1 comment · Fixed by #30483 or #30509
Labels
QA : Not Needed Release : 24.11.11 Team : Scout Type : Defect

Comments

@dcolina
Copy link
Contributor

dcolina commented Oct 29, 2024 •
edited
Loading

Parent Issue

No parent issue identified.

Problem Statement

The deployment of the artifact in the Publish Starter workflow is failing due to incorrect credentials being used. Currently, the workflow is pointing to the "trunk" environment instead of the appropriate "release" credentials. This misconfiguration is causing authentication issues and preventing successful deployment.

Steps to Reproduce

  1. Trigger the Publish Starter workflow for artifact deployment.
  2. Observe the deployment failure due to incorrect credentials, which currently point to the "trunk" environment.

Acceptance Criteria

  1. Update the workflow to use "release" credentials instead of "trunk" for the Publish Starter deployment.
  2. (Improvement) Create a separate environment named "starter" to control and log workflow traces more effectively. This will provide better tracking and segregation of the deployment process.

dotCMS Version

Not applicable.

Proposed Objective

Quality Assurance

Proposed Priority

Priority 1 - Show Stopper

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No external links provided.

Assumptions & Initiation Needs

  1. Ensure access to the "release" environment credentials and update the workflow configuration accordingly.
  2. Optionally, set up a "starter" environment for dedicated trace logging and controlled execution.

Quality Assurance Notes & Workarounds

Currently, there is no workaround. The workflow configuration must be updated to use the correct credentials.

Sub-Tasks & Estimates

  • Update the Publish Starter workflow to use "release" environment credentials.
  • Test the deployment process to ensure the issue is resolved.
  • (Optional) Create a "starter" environment for isolated trace logging and deployment control.
  • Validate the deployment and logging improvements in the new environment.
@dcolina dcolina converted this from a draft issue Oct 29, 2024
@dcolina dcolina self-assigned this Oct 29, 2024
dcolina added a commit that referenced this issue Oct 29, 2024
@dcolina
#30482 Publish Starter workflow is now pointing to a 'starter' enviro…
b87265a 
…nment and getting the repo level credentials.
@dcolina dcolina mentioned this issue Oct 29, 2024
Merged
@dcolina dcolina linked a pull request Oct 29, 2024 that will close this issue
fix(deployment): Publish Starter deployment failure due to incorrect credentials (#30482) #30483
Merged
@github-actions GitHub Actions
Copy link

github-actions bot commented Oct 29, 2024 •
edited
Loading

PRs:

github-merge-queue bot pushed a commit that referenced this issue Oct 29, 2024
@dcolina
fix(deployment): Publish Starter deployment failure due to incorrec (#…
fecc637 
…30482) (#30483)

### Proposed Changes
* The workflow is now pointing to a new environment and using repo level
credentials to complete the deployment phase.

### Additional Info
This PR resolves #30482 (Publish Starter deployment failure due to
incorrect credentials).
@github-project-automation github-project-automation bot moved this from Current Sprint Backlog to Internal QA in dotCMS - Product Planning Oct 29, 2024
@rjvelazco rjvelazco moved this from Internal QA to In Progress in dotCMS - Product Planning Oct 30, 2024
@rjvelazco rjvelazco reopened this Oct 30, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Current Sprint Backlog in dotCMS - Product Planning Oct 30, 2024
@rjvelazco rjvelazco moved this from Current Sprint Backlog to In Progress in dotCMS - Product Planning Oct 30, 2024
dcolina added a commit that referenced this issue Oct 30, 2024
@dcolina
#30482 all the environment references pointing to 'starter'.
ae48426
@dcolina dcolina mentioned this issue Oct 30, 2024
Merged
@nollymar nollymar linked a pull request Oct 30, 2024 that will close this issue
fix(deployment): Publish Starter deployment failure due to incorrect credentials (#30482) #30509
Merged
github-merge-queue bot pushed a commit that referenced this issue Oct 31, 2024
@dcolina
fix(deployment): Publish Starter deployment failure due to incorrect …
c0a01e6 
…credentials (#30482) (#30509)

### Proposed Changes
* Fixing all the environment references to 'starter'.
* A new option to include or not old assets.

### Additional Info
Related to #30482 (Publish Starter deployment failure due to incorrect
credentials).
@github-project-automation github-project-automation bot moved this from In Review to Internal QA in dotCMS - Product Planning Oct 31, 2024
@dcolina dcolina removed their assignment Oct 31, 2024
@nollymar nollymar moved this from Internal QA to Done in dotCMS - Product Planning Oct 31, 2024
dsolistorres pushed a commit that referenced this issue Nov 5, 2024
@dcolina @dsolistorres
fix(deployment): Publish Starter deployment failure due to incorrect …
718f150 
…credentials (#30482) (#30509)

### Proposed Changes
* Fixing all the environment references to 'starter'.
* A new option to include or not old assets.

### Additional Info
Related to #30482 (Publish Starter deployment failure due to incorrect
credentials).
spbolton pushed a commit that referenced this issue Nov 11, 2024
@dcolina @spbolton
fix(deployment): Publish Starter deployment failure due to incorrec (#…
b749a32 
…30482) (#30483)

### Proposed Changes
* The workflow is now pointing to a new environment and using repo level
credentials to complete the deployment phase.

### Additional Info
This PR resolves #30482 (Publish Starter deployment failure due to
incorrect credentials).
spbolton pushed a commit that referenced this issue Nov 11, 2024
@dcolina @spbolton
fix(deployment): Publish Starter deployment failure due to incorrect …
f5b54e2 
…credentials (#30482) (#30509)

### Proposed Changes
* Fixing all the environment references to 'starter'.
* A new option to include or not old assets.

### Additional Info
Related to #30482 (Publish Starter deployment failure due to incorrect
credentials).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
QA : Not Needed Release : 24.11.11 Team : Scout Type : Defect
Projects
dotCMS - Product Planning
Archived in project
Milestone
No milestone
4 participants
@nollymar @dcolina @rjvelazco @dotCMS-Machine-User