Skip to content
This repository has been archived by the owner on May 31, 2023. It is now read-only.

datasources: Allow additional datasources to be created later #46

Merged
merged 1 commit into from
Mar 23, 2018

Conversation

odyssey4me
Copy link
Collaborator

Currently the role only allows the datasources to be configured
on the first implementation. From then on if there are any data
sources configured, the task to upload any new configuration is
ignored.

This patch implements a validation for each datasource item to
check whether it's already configured using the name as the key.
If the item is not configured, it will configure it.

Currently the role only allows the datasources to be configured
on the first implementation. From then on if there are any data
sources configured, the task to upload any new configuration is
ignored.

This patch implements a validation for each datasource item to
check whether it's already configured using the name as the key.
If the item is not configured, it will configure it.
@paulfantom paulfantom self-requested a review March 22, 2018 23:55
@paulfantom paulfantom merged commit 0c5e970 into cloudalchemy:master Mar 23, 2018
@odyssey4me odyssey4me deleted the more-than-one-datasource branch March 23, 2018 10:55
@lock
Copy link

lock bot commented Mar 24, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants