Release v5.0.0 #54
Replies: 6 comments 2 replies
-
@infra-monkey I suggest keeping |
Beta Was this translation helpful? Give feedback.
-
I've reverted the attribute name. |
Beta Was this translation helpful? Give feedback.
-
@infra-monkey Here's a summary of two potential issues identified in the current implementation:
|
Beta Was this translation helpful? Give feedback.
-
@infra-monkey I've finished running additional tests and didn’t encounter any issues. Everything looks good to go! I think we're ready to release version v5.0.0. |
Beta Was this translation helpful? Give feedback.
-
@RomanButsiy agreed. |
Beta Was this translation helpful? Give feedback.
-
Closing the discussion as it has been released. |
Beta Was this translation helpful? Give feedback.
-
I opened this discussion to discuss blocking points before releasing v5.0.0.
I'm doing some deeper test both upgrading from v4.4.6 and using v5.
So here is my first finding:
In resource
freeipa_dns_zone
there was a typo in the attributeallow_prt_sync
, in v5 I have renamed itallow_ptr_sync
in order to match the attribute name in freeipa.Therefore, upgrade from 4.4.6 to 5.0.0 will fail if
allow_prt_sync
was previously set.@RomanButsiy should I keep the typo in v5 in order to facilitate the upgrade and mark it as deprecated?
Or just keep it as is because managing both attributes is a mess with default values.
Beta Was this translation helpful? Give feedback.
All reactions