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

Import testing #5

Merged
merged 4 commits into from
Oct 14, 2020
Merged

Import testing #5

merged 4 commits into from
Oct 14, 2020

Conversation

alkar
Copy link
Contributor

@alkar alkar commented Oct 14, 2020

Enable import testing and resolve an issue with imported MCR v2 resources where
a perpetual diff occurs due to the way the "term" attribute is handled.

alkar added 3 commits October 14, 2020 11:23
The previous regex returns two locations.

Signed-off-by: Dimitrios Karagiannis <[email protected]>
Cloud VXCs ignore b_end.0.product_uid values. See commit
4899cb1 for an explanation.

Signed-off-by: Dimitrios Karagiannis <[email protected]>
Even though MCRv2 does not have a "term" attribute, the API will always
return the value `1` for the respective field, which is also the default
value. We should not skip updating this field in the state for MCR v2,
when reading from the Megaport API.

If an MCRv2 is imported, the value will be `null` in state since there
is no configuration being parsed. Therefore, this generates a perpetual
diff. Updating based on the API will set the default value and prevent
this situation.

Signed-off-by: Dimitrios Karagiannis <[email protected]>
Signed-off-by: Dimitrios Karagiannis <[email protected]>
@alkar alkar merged commit 1000544 into master Oct 14, 2020
@alkar alkar deleted the import-testing branch October 14, 2020 13:53
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