plone

rubygem-hiera-3.4.2-1.lbn25.noarch
A pluggable data store for hierarcical data.
Located in LBN / … / Cloud Computing / BastionLinux 25
rubygem-hiera-aws-parameter-store-0.1.0-1.lbn25.noarch
Configuration hiera-aws-parameter-store configuration is quite simple. It uses default AWS connection and the following parameters: prefix : prefix used to find parameters in AWS Parameter Store. Mandatory. max_results : maximum number of results per AWS Parameter Store request. Default value is 50 (which is the maximum at 2017-01-21). Here is a sample hiera.yaml: --- :backends: - aws_parameter_store :aws_parameter_store: :prefix: puppet. :max_results: 50 :logger: console AWS credentials You need AWS credentials in order to access to AWS Parameter Store. The following policy shows you the required permissions: { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "ssm:DescribeParameters" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "ssm:GetParameters" ], "Resource": "arn:aws:ssm:{region}:{account}:parameter/{prefix}*" } ] } where: region: AWS region in which parameters are stored. account: your AWS account. prefix: prefix for those parameters you want to access from Hiera. E.g. if you want to organize your parameters starting with puppet., you have to use this as prefix. As an example, you can have parameters like: puppet.myapp.version. Conversions between AWS Parameter Store and Hiera types In AWS Parameter Store are present the following types: String: if the parameter name does not contains dots (.), the resulting hiera object is a String with parameter's value. If it contains dots, it's splitted and converted into a hash of objects with the last element as a string. String List: Converted into an array. Secure String: Not compatible yet. Examples: myappname=MyAppName (String) -> hiera('myappname') = "MyAppName" (String) myapp.name=MyAppName (String) myapp.version=1.3 (String) -> hiera_hash('myapp') = {"name"=>"MyAppName","version"=>"1.3"} (Hash) mylist=e1,e2,e3 (String List) -> hiera('mylist') = ["e1","e2","e3"] myapp.name=MyAppName (String) myapp.list=1,2,3 (String List) -> hiera_hash('myapp') = {"name"=>"MyAppName","list"=>["1",
Located in LBN / … / Cloud Computing / BastionLinux 25
rubygem-hiera-eyaml-2.1.0-1.lbn25.noarch
Hiera backend for decrypting encrypted yaml properties.
Located in LBN / … / Cloud Computing / BastionLinux 25
rubygem-hiera-eyaml-kms-0.1-1.lbn25.noarch
AWS KMS encryptor for use with hiera-eyaml.
Located in LBN / … / Cloud Computing / BastionLinux 25
rubygem-hiera-http-eyaml-0.9.0-1.lbn25.noarch
Fork of the Hiera HTTP backend with eYAML support.
Located in LBN / … / Cloud Computing / BastionLinux 25
rubygem-hiera-vault-0.2.2-1.lbn25.noarch
Hiera backend for looking up secrets stored in Vault.
Located in LBN / … / Cloud Computing / BastionLinux 25
zope-Record-3.4-1.lbn19.noarch
Special Record objects used in Zope2.
Located in LBN / … / Plone and Zope / BastionLinux 19
Products.AddRemoveWidget-1.5.0-3.lbn25.noarch
This is a replacement for KeywordWidget which permits you to add items from a vocabulary (and optionally new items) using a pair of selection boxes with "add" and "remove" buttons to transfer items between them. It overlaps in functionality with InAndOutWidget, but does not suffer from InAndOut's requirement for all items in the "target" list to be selection upon form submission. I believe InAndOut does not allow textual items to be added by the user, though it does support adding of referenced objects, which AddRemove does not. You are advised to test both to find out which one is more suitable for your needs. Please see the docstring in AddRemoveWidget.py for a list of options you may pass to the widget to configure it. You can also use the widget standalone, by defining a couple of variables (notably fieldName and vocabulary) and include the macro add_remove_box from widget_addremove.pt. See the comment in that file for details. Also included is a ComboBoxWidget - it can be seen as supporting the same use case, when only one item may be selected. It presents a selection box from which to select a value, and a text box to enter an "other" value if none of the items in the list are sufficient. Again, see the docstring in ComboBoxWidget.py, and the comment in widget_combobox.pt for details on how to use it within and outside Archetypes.
Located in LBN / … / Plone and Zope / BastionLinux 25
Products.AttachmentField-1.4.5-3.lbn25.noarch
An Archetype field that manages file attachments, to be used in place of a FileField. AttachmentField allows you to index and preview various kinds of documents, such as MSOffice (Word, Excel, Powerpoint), PDF and more in your Archetypes based content types. This product replaces the former ZAttachmentAttribute from Ingeniweb (see ingeniweb.sourceforge.net).
Located in LBN / … / Plone and Zope / BastionLinux 25
Products.BastionBanking-5.0.0-1.lbn25.noarch
Zope Banking tools and API's, including our ZCurrency class.
Located in LBN / … / Plone and Zope / BastionLinux 25

« Previous 10 items Next 10 items » 1 ... 4587 4588 4589 4590 4591 4592 4593 ... 4868

Sections

Search results


	Copyright © 2000-2025 Corporation of Balclutha Inc. All rights reserved.