What's an example of a dynamic parameter vs a static parameter as mentioned here?
Here are some important points you should know about working with parameters in a DB parameter group:
When you change a dynamic parameter and save the DB parameter group, the change is applied immediately regardless of the Apply Immediately setting. When you change a static parameter and save the DB parameter group, the parameter change will take effect after you manually reboot the DB instance.
http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_WorkingWithParamGroups.html
Open up and look at a parameter group in the console, or use aws rds describe-db-parameters, as documented on link you provided.
Each parameter is labeled as being static or dynamic, in both of these places.
In addition to what #Michael - sqlbot said (I can't comment, tried to edit but was justifiably rejected)
This label represents -
ApplyType -> (string)
Specifies the engine specific parameters type.
https://docs.aws.amazon.com/cli/latest/reference/rds/describe-db-parameters.html#output:~:text=value.-,ApplyType
Related
I have created a parameter in the linked service of the oracle database connection and would like to get the value of the parameter to all datasets, I have created datasets for each table and would like to get oracleSchemeName parameter from the Linked service, In my scenario schema name will change based on environments, SO I passed schema name as parameter but when I'm trying to read the value of linked service, I am getting error table or view doesn't exist.
Can someone please guide me on how to provide expression here? {#linkedService().oracleSchemaName} --Not working.
Below is the screenshot of dataset
{#linkedService().SchemaName} is invalid as schema name is not part of the linked service connection string. You can parameterize the properties which are part of the linked service connection string properties.
Example:
If you want to pass the schema/table name dynamically, you can create a pipeline level parameter and pass the values in run time.
Steps to pass the table schema value dynamically at runtime:
Create a parameter at database level (SchemaName) and do not pass any value to it currently.
Edit the table and pass dataset parameter in add dynamic content.
Create a parameter at pipeline level and add the parameter dynamically in sink properties and do not pass any value to the parameter currently.
While running the pipeline, it will ask to pass value to the pipeline parameter, then pass the value and run the pipeline.
Reference: Parameterize linked services
I've been trying to set the value of a parameter, based on the value I set of another parameter. This wasn't working but then I discovered the Parameters with Functions JSON example on the Azure GitHub
This is giving the same behaviour as my own template so is perfect to show the issues I am having.
As you can see from the JSON linked to above, the parameter hostingPlanName should concat the parameter siteName with the string -plan. When I edit the parameter file, I see the function instead of the value it resolves to.
This example pulls other values in to set the value of siteName, I wondered if that was the reasons so hard set siteName to 'TEST' and the result for hostingPlanName was the same.
I haven't deployed this example, but if I deploy my real template, it throws an error with Bad Request for the name of the resource I am deploying.
Is this me or is this not possible anymore?
I am using VS2019 Community.
This is a great place to use variables. Your hostingPlanName is not set directly by user input (as parameters should be), but is a dynamic evaluation of a complex value based on a parameter, so it should be a variable.
Looking for something to change a mode or parameter based on value of register bit(s). Something like an 'on_modify' for a bit collection. Does that already exist?
I don't think so, though the reverse (update a parameter and have it reflected in the register) is supported if that is any good to you.
See the last example about binding register bits to a live parameter here - http://origen-sdk.org/origen//guides/models/parameters/#Live_Updating_Parameters
Adding some new functionality to bit collection so that it supported something like the following API should not be too difficult:
my_reg.my_bits.on_data_changed do |data|
do_something.based_on(data)
end
The on_data_changed method would just store the given block in the bit collection instance and then trigger it whenever the write method is called.
Is it possible to pass data into UI extensions assignments (meaning UI Extension X assigned to Field Y), in order to alter their functionality slightly for different situations, without having to reimplement the entire extension?
For example, CodeMirror is a really neat embedded editor, but it has a bunch of "modes," depending on what language you're working with. If we could even pass in a string to represent the desired mode when the extension is assigned to a field, that would remove the need to do a different extension just to use different syntax highlighting.
With this, there could now be a generic "CodeMirror Editor" UI extension which is then just configured a runtime.
On the other end of the extreme, we could specify entire JSON objects when the extension is assigned to a field, to further specify configuration options.
This would make UI extensions so much more...useful. Does this functionality exist now, or is there some way to reasonably make it work? Is there some place on the field specification where I can "park" a JSON string, then access it from inside the extension?
Contentful has launched something called "Configuration parameters" for UI extensions that could be used to solve this issue.
They have two types of parameters, installation and instance parameters. Installation parameters are set when installing the UI extension, and instance parameters are set when configuring a field on a content type to use the extension. The latter would be perfect for your use case.
To use this feature you need to:
Create a parameter definition for the UI extension in the extension.json file. E.g. a new instance parameter called "codeMirrorSettings" of type Symbol with name "CodeMirror Settings".
Within the extension, fetch the current parameters using extensionsApi.parameters.instance.codeMirrorSettings.
Documentation for configuration parameters can be found in Contentful's docs:
https://www.contentful.com/developers/docs/references/content-management-api/#/reference/ui-extensions/configuration-parameters
https://github.com/contentful/ui-extensions-sdk/blob/master/docs/ui-extensions-sdk-frontend.md#extensionparameters
What you could do is just read this setting from another field, be that a string or a json object.
For example the slug generator automatically generates its value from the title field.
You could perhaps do something like this:
const cfExt = window.contentfulExtension || window.contentfulWidget
cfExt.init(api => {
var langField = api.entry.fields.mirrorLang || 'default'
//Rest of implementation
})
Well, I wrote something for this, specific to my situation, but generalizable to others. This is an example if a UI extension that retrieves settings from another entry in the space, and uses it to dynamically configure itself.
https://github.com/deanebarker/contentful-code-editor
I have an xPage with multiple instances of the same custom control. How do I get to the value of a field on a specific custom control from a button on my xPage.
Normally I would do something like:
ctlName = "radioGroupCMBUAction";
var changeType = getComponent(ctlName).getValue();
If there was only one instance of the control. How would I do this with multiple instances of the control?
Without the code I'm not sure if .getValue() will work as in order for this to happen it will have to pull out a field where as a custom control could have a repeat inside it etc.
Assuming that it will work if each of the customControl instances have an id that is unique from each other it should work fine as each instance should have its own vriables inside it.
Other ideas however could be to pass in a string and use this string as the name of a scoped variable inside the custom control that can be pulled out from anywhere. I've done this before where I created a property on the custom control for a String and inside the custom control use
viewScope[compositeData.customProperty] = value.
then outside the context of the custom control I am aware of the string I passed in so I would be able to pull this value back out. Passing it in means multiple instances won't over write each other.
Or you could write the field in he custom control to a document, either to get it out or as the end solution to your problem of saving it.
Not sure if this can help you..? A while back, I wrote a tip regarding "private" scoped variables:
http://dontpanic82.blogspot.com/2010/03/xpages-tip-regarding-private-scoped.html