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

Update ioc_changes1.rst #59

Merged
merged 1 commit into from
Nov 14, 2023
Merged

Conversation

marcelldls
Copy link
Contributor

Running ec deploy bl01t-ea-ioc-02 2023.11.2 results in No such command 'deploy'

Correct missing command option
@marcelldls
Copy link
Contributor Author

Also regarding the comment "# deploy the new version of the IOC to the local docker / podman instance"... Is that not the intention of the command ec ioc deploy-local? I believe in this case it just happens to be on the local machine

Copy link
Member

@gilesknap gilesknap left a comment

Choose a reason for hiding this comment

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

I keep making this mistake with my own use of ec. So much so that in considering dropping the ioc namespace and promoting all ioc commands to the root namespace.

The dev namespace could remain but is not used so much now that we have a great Dev containers solution.

What do you think? (Mean time in merging your pr as it is correct for current ec)

@gilesknap gilesknap merged commit 7c94c5f into epics-containers:main Nov 14, 2023
1 check passed
@marcelldls
Copy link
Contributor Author

I quite like the namespaces because it feels more explicit - but what you have suggested also makes sense. I have no strong opinion at this stage

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.

2 participants