Skip to content

Conversation

@hayemaxi
Copy link
Contributor

@hayemaxi hayemaxi commented Jan 15, 2025

This code removes nearly all cloud9 codepaths:

  • Icons, readme generation, scripts
  • ikp3db lambda/sam debugger support
  • Cloud9 only codepaths and hacks
  • Docs and comments mentioning Cloud9

Includes some follow up items as TODOs in code.

Some items were left in case they are helpful in the future (e.g. for vscode web or similar). The items should be renamed from Cloud9 if used again in the future. Some examples are Cloud9 runtime environment checks (for lambda/sam), isCloud9() and properties/text for Cloud9 IDE, some SAM artifacts, don't start LSP server, etc. Search cloud9 in vscode after merging this change.


  • Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
  • Your code changes must meet the guidelines in CONTRIBUTING.md.
  • License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

These keys are currently set by the core/ package, but many of them may eventually be migrated to
toolkit/ or amazonq/ if appropriate.

- `isCloud9`: This is hardcoded by Cloud9 itself, not the Toolkit.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

package.json updates will be a separate PR

@hayemaxi hayemaxi changed the title revert: remove cloud9 related code revert: cloud9 related code Jan 15, 2025
hayemaxi added a commit to hayemaxi/aws-toolkit-vscode that referenced this pull request Jan 15, 2025
@hayemaxi hayemaxi marked this pull request as ready for review January 15, 2025 23:14
@hayemaxi hayemaxi requested review from a team as code owners January 15, 2025 23:14
"id": "aws.amazonq.notifications",
"name": "%AWS.notifications.title%",
"when": "!isCloud9 && !aws.isSageMaker && aws.amazonq.notifications.show"
"when": "!aws.isSageMaker && aws.amazonq.notifications.show"
Copy link
Contributor

@justinmk3 justinmk3 Jan 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Anything that applies to sagemaker potentially applies to isCloud9CodeEditor. This looks like such a case.

for now, we can either leave this as isCloud9 and create a backlog issue to revisit the remaining isCloud9 cases like this, or rename it to isCloud9CodeEditor (or whatever we call it)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These seem to be leftover artifacts from notifications development. I have fixed them, but left isCloud9 to revisit later.

const editCreds = messages.editCredentials(false)
// TODO: getHelp page for Cloud9.
const buttons = isCloud9() ? [editCreds] : [editCreds, getHelp]
const buttons = [editCreds, getHelp]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems like something we should either leave or leave a todo comment with a token that we can find later. because we don't want to show vscode-related messaging.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The related link is not vscode related: https://docs.aws.amazon.com/signin/latest/userguide/differences-aws_builder_id.html

The auth story for a Cloud9CodeEditor is unclear though. A todo to verify would be better.


// Only used in rare cases on C9
export const reauth = Commands.declare(
'_aws.codecatalyst.reauthenticate',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we delete the command code?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No because the comment was wrong, it's used here:

reauth.build(auth.activeConnection, auth).asTreeNode({

}
}

// TODO: Delete? as it was only used in Cloud9
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, we dropped the "quickstart" concept, which had overlap with (1) the marketplace readme, and (2) the new notifications / whats-new concept.

/**
* Temporary util while Cloud9 does not have codicon support
*/
export function addCodiconToString(codiconName: string, text: string): string {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

might be able to drop this function, maybe a comment that mentions "cloud9" should stay on it

This code removes nearly all cloud9 codepaths:
- Icons, readme generation, scripts
- ikp3db lambda/sam debugger support
- Cloud9 only codepaths and hacks
- Docs and comments mentioning Cloud9

Includes some follow up items as TODOs in code.

Some items were left in case they are helpful in the future (e.g. for vscode web or similar). The items should be renamed from Cloud9 if used again in the future.
Some examples are Cloud9 runtime environment checks (for lambda/sam), `isCloud9()` and properties/text for Cloud9 IDE, some SAM artifacts, don't start LSP server, etc. Search cloud9 in vscode after merging this change.
…252-be69-9a0684406944.json

Co-authored-by: Justin M. Keyes <[email protected]>
@hayemaxi hayemaxi merged commit 01351dd into aws:master Jan 21, 2025
24 of 26 checks passed
kevluu-aws pushed a commit to kevluu-aws/aws-toolkit-vscode that referenced this pull request Jan 23, 2025
This code removes nearly all cloud9 codepaths:
- Icons, readme generation, scripts
- ikp3db lambda/sam debugger support
- Cloud9 only codepaths and hacks
- Docs and comments mentioning Cloud9

Includes some follow up items as TODOs in code.

Some items were left in case they are helpful in the future (e.g. for
vscode web or similar). The items should be renamed from Cloud9 if used
again in the future. Some examples are Cloud9 runtime environment checks
(for lambda/sam), `isCloud9()` and properties/text for Cloud9 IDE, some
SAM artifacts, don't start LSP server, etc. Search cloud9 in vscode
after merging this change.

---

- Treat all work as PUBLIC. Private `feature/x` branches will not be
squash-merged at release time.
- Your code changes must meet the guidelines in
[CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

---------

Co-authored-by: Justin M. Keyes <[email protected]>
chungjac pushed a commit to chungjac/aws-toolkit-vscode that referenced this pull request Jan 24, 2025
This code removes nearly all cloud9 codepaths:
- Icons, readme generation, scripts
- ikp3db lambda/sam debugger support
- Cloud9 only codepaths and hacks
- Docs and comments mentioning Cloud9

Includes some follow up items as TODOs in code.

Some items were left in case they are helpful in the future (e.g. for
vscode web or similar). The items should be renamed from Cloud9 if used
again in the future. Some examples are Cloud9 runtime environment checks
(for lambda/sam), `isCloud9()` and properties/text for Cloud9 IDE, some
SAM artifacts, don't start LSP server, etc. Search cloud9 in vscode
after merging this change.

---

- Treat all work as PUBLIC. Private `feature/x` branches will not be
squash-merged at release time.
- Your code changes must meet the guidelines in
[CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

---------

Co-authored-by: Justin M. Keyes <[email protected]>
s7ab059789 pushed a commit to s7ab059789/aws-toolkit-vscode that referenced this pull request Feb 19, 2025
This code removes nearly all cloud9 codepaths:
- Icons, readme generation, scripts
- ikp3db lambda/sam debugger support
- Cloud9 only codepaths and hacks
- Docs and comments mentioning Cloud9

Includes some follow up items as TODOs in code.

Some items were left in case they are helpful in the future (e.g. for
vscode web or similar). The items should be renamed from Cloud9 if used
again in the future. Some examples are Cloud9 runtime environment checks
(for lambda/sam), `isCloud9()` and properties/text for Cloud9 IDE, some
SAM artifacts, don't start LSP server, etc. Search cloud9 in vscode
after merging this change.

---

- Treat all work as PUBLIC. Private `feature/x` branches will not be
squash-merged at release time.
- Your code changes must meet the guidelines in
[CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

---------

Co-authored-by: Justin M. Keyes <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants