-
Notifications
You must be signed in to change notification settings - Fork 216
Remove run.sh and its mentions #745
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
Conversation
site/v1.1/README.md
Outdated
@@ -167,7 +167,7 @@ For information about how to shut down a domain running in Kubernetes, see [Shut | |||
|
|||
To permanently remove the Kubernetes resources for a domain from a Kubernetes cluster, run the [Delete WebLogic domain resources](/kubernetes/delete-weblogic-domain-resources.sh) script. This script will delete a specific domain, or all domains, and all the Kubernetes resources associated with a set of given domains. The script will also attempt a clean shutdown of a domain’s WebLogic pods before deleting its resources. You can run the script in a test mode to show what would be shutdown and deleted without actually performing the shutdowns and deletions. For script help, use its `-h` option. | |||
|
|||
The script will remove only domain-related resources which are labeled with the `domainUID` label, such as resources created by the [Create WebLogic domain](/kubernetes/create-weblogic-domain.sh) script or the [integration tests](/src/integration-tests/bash/run.sh). If you manually created resources and have not labelled them with a `domainUID`, the script will not remove them. One way to label a resource that has already been deployed is: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we should remove the references to run.sh from V1.1 doc because run.sh is only removed in V2.0.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A question: why release V1.1 doc in 2.0 source code?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@markxnelson @rjeberhard I don't remember the details about this. can you also confirm if my understanding/comments are correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The 1.1 docs were preserved so you could see the documentation for that release. In general, I agree that we should not change the historical documents.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM Apart from the changes to 1.0/1.1 doc files that Dongbo noticed - I think those should simply be left unchanged.
Jenkins passed. http://****/job/weblogic-kubernetes-operator-javatest/801/