When I run the export command here below it creates a new export folder containing a set of JSON files that corresponds to the different apps and organisations I have.
$ java -jar usergrid-tools.jar export
Unluckly the Assets (files) I've stored are not exported, how do I export them?
Exporting assets is not supported at this time. I have opened a ticket in our JIRA and you can track it here: https://issues.apache.org/jira/browse/USERGRID-997
Related
Let's say I have an invoice to generate and the invoice contains the company's logo and other images that would be used each time an invoice is generated.
Would I have to pull those images off the storage bucket? Or can I load it into the functions directory and use it from there, similar to how the serviceaccount.json file is loaded into functions?
EDIT: The way I'm thinking of is
functions/
├── index.js
├── image.jpg
And in index.js
const path = require("path");
const pathToImage = path.join(__dirname,'/image.jpg');
The Firebase/Cloud Functions deployment process packs up everything in your functions directory, and deploys it to the runtime for your functions. This means that you can indeed include any static files you need in the Cloud Functions deployment, and then access them from your code.
This is how you also include your service account, or what happens when you split your Cloud Functions code over multiple files that you then include into index.js.
I have multiple Openstack projects available but every command I execute only is applied to my personal project.
I would like to know how to change the "working project". I do not seem to find it in the docs.
I don't know what interface is used by you, I'll provide an solutions based CLI.
'openstackrc_youraccount' file (it's ocata version rc file, but important variable is OS_PROJECT_NAME. OS_TENANT_NAME is old version name.)
export OS_USERNAME=YOUR_USERNAME
export OS_PASSWORD=YOUR_PASS
export OS_PROJECT_NAME=YOU_WANT_TO_WORK_PROJECT_NAME
export OS_USER_DOMAIN_NAME=Default
export OS_PROJECT_DOMAIN_NAME=Default
export OS_AUTH_URL=http://YOUR_CONTROLLER_HOST_OR_IP:35357/v3
export OS_IDENTITY_API_VERSION=3
After setting up the project name where you want to work into OS_PROJET_NAME, and then applying the current session.
$ source openstackrc_youraccount
Now you can work at the project you selected.
I hope it helpful to you.
Is there a way in Azure Resource manager to take a copy of an existing database? Currently I know there is a database import option, which points to a bacpac file in Blob Storage and creates a new database from that file, but the process to create the file is a manual one at this point. With that, what is the current process to create bacpacs and put them in Blob storage in an automated way through ARM?
There is a way to specify the createMode of your database in the ARM template. This is very undocumented stuff but I found this in the REST api documentation and then just tried in the ARM template.
You can specify the properties "createMode" and "sourceDatabaseId".
I am not using this functionality because the sourceDatabaseId needs to be in the same subscription which was not the case with me. So i export the bacpac manually and then use an ARM template to import the bacpac (which also is undocumented but I commented the ARM template used here: https://azure.microsoft.com/en-us/documentation/articles/sql-database-import/)
I am upgrading my drupal website's version from 6 to 7. I have used "node import" module for importing contents in druapl 6.
In drupal 7, I have installed "Feeds" module and enabled the available features.
"node import" - Here I had a option to export the failed records with error messages in each imported files.
"Feeds" - But here I have only "log" option to see the failed records as log information.
I need to give a option to user that exports the failed records for each imported files.
Do the drupal provides any modules/hooks ? or I need to customize the code itself ?
Thanks,
Create a view with the failed nodes (using appropriate filters), and use Views Data Export module to export as CSV, with the format required.
This module is designed to provide a way to export large amounts of data from views. It provides a display plugin that can rendered progressively in a batch. Style plugins are included that support exporting in the following types:
CSV
Microsoft XLS
Microsoft DOC
Basic TXT
XML.
If you are new to this module, there is a very good documentation at : https://drupal.org/node/1820452
We have large number of publications and currently we manually apply the CMS permissions across multiple environments (UAT and PROD mainly). This is tedious and often times error prone.
We are trying to export and import the CMS permissions across multiple environments, so this could be done once manually and ported to other environments using some sort of tool.
Environment: Tridion 2011 SP1 + IIS 7.5 + SQL Server 2008 r2
In Old PowerTools (VBScript) there used to be some tool to manage Access management which could be handy, still error prone. We are not interested to use the OLD powertools for obvious reasons and it is recurring operation function so DB option is ruled out as well.
We are considering to build a tool using Core Service, that could export and Import the permissions. We have the same Groups, Publications and Folder structure across these environments.
Has anyone tried this before? What are the experiences or practices that other fellow Tridioneers used in large implementations.?
Any view points are greatly appreciated.
I once wrote a tool that allowed you to describe your desired permissions settings as JSON, and apply them via the API. To be honest, if you were to write a DTAP-security tool, I'd follow a similar approach. Start by being able to express your desired settings in an open, text-based format, then write a tool that imports them. Once you have this, you can easily build a tool that exports them.
I created a security migration tool in Tridion 5.2 but the solution approach will still apply to current versions of Tridion
Summary
The solution used a set of simple vbscript export page templates to extract the security information as xml and store it in a set of components.
I then used Tridion Content Porter to move these security components, page templates and tbbs's to the target CMS's
Using set of simple import page templates to open the security xml components to apply the security setting to the target cms.
The tcmid's will be different in the target cms so the import functions must use webdav urls and build dictionaries of tcmid's for trustees etc
Details
Export Security Groups
iterate selected Groups
append group xml
save xml in component
Export Publication Rights
getlistpublications
iterate list of publications
get each publication xml
remove "//tcm:CategoriesXSD" node
appendChild publication xml
remove unwanted "//tcm:Trustee" nodes
save xml in component
Export Folder Permissions
recursively iterate folders
append Folder XML
remove trustee nodes that are inherited ("IsInheritanceRoot")
save xml in component
Export Structure Group Permissions
recursively iterate Structure groups
append structure group XML
remove metadata node "//tcm:Metadata"
filter out unwanted Trustees
save xml in component
Import Security Groups
load xml from security component
iterate group nodes
create groups if they don't already exist
Import Publication rights
load xml from security component
update xml tcmid's
iterate publications
load publication xml
build xml updategram
update publication xml
Import Folder Permissions
load xml from security component
update xml tcmid's
for each folder node
build updategram xml
open folder
update folder xml
Import Structure Group Permissions
load xml from security component
update xml tcmid's
for each structure group node
build updategram xml
open structure group
update structure group