-
Notifications
You must be signed in to change notification settings - Fork 75
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
Datastore import - name source #392
Comments
@pkomanek Can you provide a link to where you identified this issue in the code, thanks. |
@gmcculloug sure.
|
This issue has been automatically marked as stale because it has not been updated for at least 3 months. If you can still reproduce this issue on the current release or on Thank you for all your contributions! More information about the ManageIQ triage process can be found in the traige process documentation. |
Ping @tinaafitz |
This issue has been automatically marked as stale because it has not been updated for at least 3 months. If you can still reproduce this issue on the current release or on Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation. |
I've just noticed that we are using the file name as a domain name inside our automate datastore import. For the rest of the objects we are looking into the YAML file and taking the value from the name attribute. I am not sure which way is better, but I think we should be consistent.
The text was updated successfully, but these errors were encountered: