The current template is tailored for a git-typed application.
The user just needs to input the project name to be used as the project folder.

I suggest adding another layer on top of that,
before (or after) the user inputs the project name,
he/she will select the application type, git/helm/object.

create a new OCM application folder template from the command palette

Add templates for the HelmRepo and ObjectBucket subscription types as well as the existing Git type:

https://github.com/ilan-pinto/ocm-vscode-extension/tree/main/templates/Git

add relevent details of the readme file

• intro
• release notes
• TBD

auto-complete a yaml snippet template for the following

• manifestwork
• placement
• subscription
• placementrules
• rules

In some cases, while debugging the create environment command,
it appears as if the command for accepting the managed clusters CSR by the hub, is being issued more than once.

As for the time of opening this issue, this is only demonstrated when creating 1 managed cluster,
and occasionally, it works well.

I'm not sure yet if it's a debug-only issue, an environmental issue, or a code bug.

Demonstrated with 1 managed cluster

note the CSR cluster1-jpsxr already approved after the CSR cluster1-jpsxr approved output.

Working well with 1 managed cluster

Working well for 2 managed clusters

Update the Placement CRs version to v1beta1, previous v1alpha1 is deprecated.
Needs to be done in for the snippets and the templates.

@ilan-pinto do we want to preserve older versions of CRDs?
maybe preserve only for major versions...

https://github.com/open-cluster-management-io/placement/blob/main/CHANGELOG/CHANGELOG-v0.4.md#changes

Add integration tests to the various extension capabilities.

The current subscription snippet is of a git-typed application, adding two more snippets for helm-typed and object-typed applications, should be a good idea and quite easy to accomplish.

Explore the option of adding completion and validation via schemas, much like being done for k8s with the YAML extension.

1. Define packaging extensions in CI
2. Add meta information to package.json (icon, repo and so on)

Add a .github/CONTRIBUTING.md guidelines file with development instructions.

Use JSDoc comment structure and tags.

start-up local kind dev environment from the command palette

Extend the right-click menu with an option to add OCM snippets while a YAML file is open in the editor.

TBD -
trigger clusteradm commands from VS code

The latest modifications have introduced more templates and more snippets,
the animated gits in the main README file should indicate these modifications.
https://github.com/ilan-pinto/ocm-vscode-extension/tree/main/images

Add a CI workflow to be triggered for pull requests.