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.

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

ER: update docker-compose.yml to remove warning when running docker-compose up #7772

Open
5 tasks
roslynwythe opened this issue Nov 27, 2024 · 1 comment
Open
5 tasks
Labels
Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Complexity: Small Take this type of issues after the successful merge of your second good first issue ER Emergent Request Feature: Docker Issue Making: Level 2 Make issue(s) from an ER or Epic Ready for Prioritization role: back end/devOps Tasks for back-end developers size: 0.5pt Can be done in 3 hours or less

Comments

@roslynwythe
Copy link
Member

roslynwythe commented Nov 27, 2024

Emergent Requirement - Problem

When running docker-compose up the following message appears

$ docker-compose up
time="2024-11-26T16:24:37-08:00" level=warning msg="C:\\Users\\rosly\\hfla\\website\\docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion"

According to this article, the version attribute is informative only and will result in a warning message that it is obsolete if used.

Issue you discovered this emergent requirement in

Date discovered

11/26/2024

Did you have to do something temporarily

  • YES
  • NO

Who was involved

@roslynwythe

What happens if this is not addressed

potential confusion

Resources

article

Recommended Action Items

  • Make a new issue
  • Discuss with team
  • Let a Team Lead know

Potential solutions [draft]

@roslynwythe roslynwythe added Feature Missing This label means that the issue needs to be linked to a precise feature label. size: 0.25pt Can be done in 0.5 to 1.5 hours ER Emergent Request Complexity: Missing role missing labels Nov 27, 2024
Copy link

Hi @roslynwythe.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:

  • Complexity, Role, Feature

NOTE: Please ignore this comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

@roslynwythe roslynwythe added Complexity: Medium Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Issue Making: Level 2 Make issue(s) from an ER or Epic Feature: Docker size: 1pt Can be done in 4-6 hours role: back end/devOps Tasks for back-end developers Ready for Prioritization Complexity: Small Take this type of issues after the successful merge of your second good first issue size: 0.5pt Can be done in 3 hours or less and removed Complexity: Missing Feature Missing This label means that the issue needs to be linked to a precise feature label. size: 0.25pt Can be done in 0.5 to 1.5 hours role missing Complexity: Medium size: 1pt Can be done in 4-6 hours labels Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Complexity: Small Take this type of issues after the successful merge of your second good first issue ER Emergent Request Feature: Docker Issue Making: Level 2 Make issue(s) from an ER or Epic Ready for Prioritization role: back end/devOps Tasks for back-end developers size: 0.5pt Can be done in 3 hours or less
Projects
Status: New Issue Approval
Development

No branches or pull requests

1 participant