set okteto context and namespace from env vars

[andreafalzetti]

Proposed changes

Fixes DEV-281

How to validate

You need at least 2 different contexts to validate this change.

Scenario 1 - no context

Without any current context, or --context, or OKTETO_CONTEXT the CLI should tell you that you have no context.

Try the following:

OKTETO_HOME=$(mktemp -d) okteto endpoints
# or
OKTETO_HOME=$(mktemp -d) okteto context show

And validate that you get a message in both cases saying your context is not set.

Scenario 2 - current context

Assuming you have a current context:

1. run okteto context show
2. validate that the context is correct

Scenario 3 - current context + --context flag

The flag should have priority over the current context, to validate this scenario, run:

1. run okteto context show
2. observe which context you have as current (let's callit <CTX1>)
3. Run okteto endpoints --context <CTX2>
4. the CLI should say you are using <CTX2>
5. check that the namespace is also selected correctly based on <CTX2>
6. now run: okteto endpoints --context <CTX2> --namespace <NS2>
7. check that the <NS2> is picked up as expected

Scenario 4 - current context + OKTETO_CONTEXT

1. run okteto context show
2. observe which context you have as current (let's callit <CTX1>)
3. Run OKTETO_CONTEXT=<CTX2> okteto endpoints
4. the CLI should say you are using <CTX2>
5. check that the namespace is also selected correctly based on <CTX2>
6. now run: OKTETO_CONTEXT=<CTX2> OKTETO_NAMESPACE=<NS2> okteto endpoints
7. check that the <NS2> is picked up as expected

Scenario 5 - current context + OKTETO_CONTEXT + --context

For this scenario it's ideal to use 3 different contextes to avoid ambiguities.

1. run okteto context show
2. observe which context you have as current (let's callit <CTX1>)
3. Run OKTETO_CONTEXT=<CTX2> okteto endpoints --context <CTX3>
4. the CLI should say you are using <CTX3>
5. check that the namespace is also selected correctly based on <CTX3>
6. now run: OKTETO_CONTEXT=<CTX2> OKTETO_NAMESPACE=<NS2> okteto endpoints --context <CTX3> --namespace <NS3>
7. check that the <NS3> is picked up as expected

Scenario 6 - current context + .env with OKTETO_CONTEXT + --context

1. run okteto context show
2. observe which context you have as current (let's callit <CTX1>)
3. create .env with OKTETO_CONTEXT=<CTX2>
4. Run okteto endpoints --context <CTX3>
5. the CLI should say you are using <CTX3>
6. check that the namespace is also selected correctly based on <CTX3>
7. now add OKTETO_NAMESPACE=<NS2> to the .env
8. Run: okteto endpoints --context <CTX3> --namespace <NS3>
9. check that the <NS3> is picked up as expected

Scenario 7 - current context + manifest context: + --context

1. run okteto context show
2. observe which context you have as current (let's callit <CTX1>)
3. set context: <CTX2> in your manifest
4. Run okteto endpoints --context <CTX3>
5. the CLI should say you are using <CTX2>
6. check that the namespace is also selected correctly based on <CTX2>
7. now add namespace: <NS2> in your manifest
8. now run: okteto endpoints --context <CTX3> --namespace <NS3>
9. check that the <NS2> is picked up as expected

Scenario 8 - current context + OKTETO_URL

1. run okteto context show
2. observe which context you have as current (let's callit <CTX1>)
3. Run OKTETO_URL=<CTX2> okteto endpoints
4. the CLI should say you are using <CTX2>
5. check that the namespace is also selected correctly based on <CTX2>
6. now run: OKTETO_URL=<CTX2> OKTETO_NAMESPACE=<NS2> okteto endpoints
7. check that the <NS2> is picked up as expected

Out of scope scenarios:

These are lower-priority scenarios that may be worked on with a follow-up ticket/PR.

• Scenario 8 - current context + OKTETO_CONTEXT var set in Catalog
• Scenario 9 - current context + OKTETO_CONTEXT var set in Catalog + --context
• Scenario 10 - current context + OKTETO_CONTEXT set as --var flag in deploy
• Scenario 11 - current context + OKTETO_CONTEXT set as User variable
• Scenario 12- current context + OKTETO_CONTEXT set as Cluster variable

CLI Quality Reminders 🔧

For both authors and reviewers:

• Scrutinize for potential regressions
• Ensure key automated tests are in place
• Build the CLI and test using the validation steps
• Assess Developer Experience impact (log messages, performances, etc)
• If too broad, consider breaking into smaller PRs
• Adhere to our code style and code review guidelines

[maroshii]

I don't have enough context in the CLI or understand how context works internally to confidently approve this PR. Deferring approval to @jLopezbarb

[andreafalzetti]

Moving to draft until e2e are passing

[jLopezbarb]

LGTM besides of the e2e tests

[codecov]

Codecov Report

Attention: Patch coverage is 6.25000% with 15 lines in your changes are missing coverage. Please review.

Project coverage is 45.64%. Comparing base (06d3161) to head (59963f7).
Report is 5 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4247      +/-   ##
==========================================
- Coverage   45.64%   45.64%   -0.01%     
==========================================
  Files         308      308              
  Lines       27849    27839      -10     
==========================================
- Hits        12711    12706       -5     
+ Misses      14040    14035       -5     
  Partials     1098     1098              

[maroshii]

This looks like quite a sensitive change for a backport