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

(POOLER-92) Add the alias information in the API status page for each… #244

Merged
merged 2 commits into from
Oct 20, 2017

Conversation

sbeaulie
Copy link
Contributor

@sbeaulie sbeaulie commented Oct 18, 2017

… pool

Before this change if a pool had an alias configured, the information would not be
made public in the API. This commit adds the alias key in the pool object for each
pool if configured. The alias key can be absent, a string or an one or multiple
array of strings. The value of the alias is copied from the configuration and can
represent another name for the pool, or another configured pool.

… pool

Before this change if a pool had an alias configured, the information would not be
made public in the API. This commit adds the alias key in the pool object for each
pool if configured. The alias key can be abscent, a string or an one or multiple
array of strings. The value of the alias is copied from the configuration and can
represent another name for the pool, or another configured pool.
Copy link
Contributor

@glennsarti glennsarti left a comment

Choose a reason for hiding this comment

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

WITH TESTS!!!

@@ -0,0 +1,74 @@
---
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this test fixture file in the right location? i.e. the root of the project? Should it be under /spec/?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's not used by the spec tests, in fact I have not seen any .yaml file in the spec directory. I want that example dummy config file in the repo to share that file with my team members working on integrating this new information into the ABS scheduler. I think the directory ex would be better for this?

Copy link
Contributor

Choose a reason for hiding this comment

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

Perhaps the docs dir?

@mattkirby mattkirby merged commit abdc86f into master Oct 20, 2017
@mattkirby mattkirby deleted the POOLER-92 branch October 20, 2017 16:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants