Clean pattern for sharing record values across multiple names
See original GitHub issueCould either be implemented in YamlProvider
or potentially use make use of yaml features like this or this.
I’d probably lean towards the yaml route as it has some pretty powerful feautres, but we’d have to make sure that they work well with PyYaml and document a suggested way to do them.
If implemented in YamlProvider
and not yaml it could potentially look something like:
---
_octodns:
templates:
www
type: A
values:
- 1.2.3.4
- 1.2.3.5
geo:
NA-US-CA:
- 2.2.3.4
- 2.2.3.5
'':
_template: www
'www':
_template: www
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:7 (7 by maintainers)
Top Results From Across the Web
10 Super Neat Ways to Clean Data in Excel Spreadsheets
In this blog post, I will show you 10 simple ways to clean data in Excel. This Tutorial Covers: ... This removes duplicate...
Read more >The Ultimate Guide to Data Cleaning | by Omar Elgabry
Many companies use customer information databases that record data ... Inconsistency occurs when two values in the data set contradict each ...
Read more >Role based sharing - unique names per team needed?
You could create sharing rules for each object based on criteria of the records (values within it) or based on who owns it....
Read more >Cleaning Data with OpenRefine | Programming Historian
Remove duplicate records ; Separate multiple values contained in the same field; Analyse the distribution of values throughout a data set ...
Read more >Sharing Rule Types - Salesforce Help
A criteria-based sharing rule is based on record values and not the record owners. However, a role or territory hierarchy still allows users...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s still on the wish-list, but not specifically on my TODO list atm. The new
dynamic
record support coming in the next few weeks/months will take a big step in this direction through “pools” and “rules” being separate concepts. That doesn’t solve the general case and things will still be scoped to a record.Happy discuss options here and look over a PR once we’ve settled on a direction. Otherwise it’s probably going to stay a wish-list item for a while longer.
Not sure how/why this is closed. Probably accidental.
I have a lot of thoughts on what sorts of templating I’d like to see after having spent more time using octoDNS for real. My biggest want is now is to actually be able to provide a set of values that get filled in on a record. We have a bunch of duplicated
value
andgeo
keys on records. This would especially be useful if it could lay out the structure (geo used etc.) and fill in the values (ips), but I’m not aware of anything in yaml’s functionality that would support that, PyYaml or not.Yeah. That’d be useful for the
geo
structure stuff mentioned above as well. All of our records with geo support have exactly the same locations pointed to the same regions, just with different IPs. I’d be nice to be able to manage that structure once and have all the records across our zones fill in the specific ips used there.Not sure when this will be looked into, but it’s definitely somewhere on the nice to have list.